Why:
Safari's Intelligent Tracking Prevention (ITP) limits cookies set via API
responses from CNAME-cloaked subdomains to 7 days. This causes unexpected
session expiration for Safari users who don't visit frequently. The new
decorateUrl function in setActive/finalize navigate callbacks enables
automatic cookie refresh when needed.

What changed:
- Updated 25 doc files with decorateUrl pattern in navigate callbacks
- Pattern wraps destination URLs and checks if result is absolute (http)
  to determine whether to use window.location.href or router.push()
- Covers all custom flows: auth, legacy auth, Expo partials
- Skipped billing checkout finalize() - different API, not affected

Files: oauth-connections, sign-in-or-up, email-password, email-password-mfa,
email-sms-otp, passkeys, enterprise-connections, legal-acceptance,
embedded-email-links, multi-session-applications, session-tasks,
error-handling, forgot-password, application-invitations, expo partials

…acks

The navigate callback receives an object { session, decorateUrl }, not
decorateUrl directly. Without destructuring, decorateUrl('/')  would
throw at runtime.

- Use `url` variable instead of hardcoded '/' in else branch (legacy/application-invitations)
- Replace `router.push` with `window.location.href` in vanilla JS examples (multi-session, clerk.mdx)
- Add missing `return` after currentTask check to prevent fall-through navigation
- Remove `window.location.href` from Expo examples where it doesn't exist in React Native